On mips, 1**np.nan and np.nan**0 may be NaN not 1
authorDebian Science Team <debian-science-maintainers@lists.alioth.debian.org>
Sun, 18 Feb 2024 20:31:18 +0000 (20:31 +0000)
committerRebecca N. Palmer <rebecca_palmer@zoho.com>
Sun, 18 Feb 2024 20:31:18 +0000 (20:31 +0000)
commite5e311e150f8058c96d88ef580780f2f4fb1fab3
tree79c4dd90d7ca6c77a7b05c03390c464e5062451d
parent731dbdae06ed90961104bdefc4536af6dfb3a32f
On mips, 1**np.nan and np.nan**0 may be NaN not 1

Done this way not a plain xfail to allow only this difference,
not clearly wrong answers

(The same hardware's "invalid value encountered" warnings,
probably from sNaN/qNaN being reversed, are ignored elsewhere:
d/rules and xfail_tests_nonintel_io.patch)

https://en.wikipedia.org/wiki/NaN#Encoding

Author: Rebecca N. Palmer <rebecca_palmer@zoho.com>
Forwarded: no

Gbp-Pq: Name mips_pow_nan.patch
pandas/tests/arrays/floating/test_arithmetic.py
pandas/tests/arrays/sparse/test_arithmetics.py